Allocating acceleration component functionality for supporting services

ABSTRACT

Aspects extend to methods, systems, and computer program products for allocating acceleration component functionality for supporting services. A service manager uses a finite number of acceleration components to accelerate services. Acceleration components can be allocated in a manner that balances load in a hardware acceleration plane, minimizes role switching, and adapts to demand changes. When role switching is appropriate, less extensive mechanisms (e.g., based on configuration data versus image files) can be used to switch roles to the extent possible.

CROSS-REFERENCE TO RELATED APPLICATIONS

Not Applicable

BACKGROUND

Computer systems and related technology affect many aspects of society. Indeed, the computer system's ability to process information has transformed the way we live and work. Computer systems now commonly perform a host of tasks (e.g., word processing, scheduling, accounting, etc.) that prior to the advent of the computer system were performed manually. More recently, computer systems have been coupled to one another and to other electronic devices to form both wired and wireless computer networks over which the computer systems and other electronic devices can transfer electronic data. Accordingly, the performance of many computing tasks is distributed across a number of different computer systems and/or a number of different computing environments. For example, distributed applications can have components at a number of different computer systems.

BRIEF SUMMARY

Examples extend to methods, systems, and computer program products for allocating acceleration component functionality for supporting services. A service manager monitors characteristics of a plurality of hardware acceleration components in a hardware acceleration plane. The hardware acceleration plane provides a configurable fabric of acceleration components for accelerating services.

The service manager allocates a group of interoperating acceleration components, from among the plurality of hardware acceleration components, to provide service acceleration for a service. The group of interoperating acceleration components is allocated based on the monitored characteristics in view of an allocation policy for the hardware acceleration plane. A role at each acceleration component in the group of interoperating acceleration components are linked together to compose a graph providing the service acceleration. The service manager maintains an address for the graph so that the service can request hardware acceleration from the group of interoperating acceleration components.

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

Additional features and advantages will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice. The features and advantages may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features and advantages will become more fully apparent from the following description and appended claims, or may be learned by practice as set forth hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and other advantages and features can be obtained, a more particular description will be rendered by reference to specific implementations thereof which are illustrated in the appended drawings. Understanding that these drawings depict only some implementations and are not therefore to be considered to be limiting of its scope, implementations will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 illustrates an example architecture that includes a software plane and a hardware acceleration plane.

FIG. 2 illustrates an example architecture, including servers, that can be used in a data center

FIG. 3 illustrates an example server.

FIG. 4 illustrates an example server.

FIG. 5 illustrates an example service implemented using components of a software plane and components of a hardware acceleration plane.

FIG. 6 illustrates an example service implemented using components of a software plane and components of a hardware acceleration plane.

FIG. 7 illustrates an example architecture of an acceleration component.

FIG. 8 illustrates an acceleration component including separate configurable domains.

FIG. 9 illustrates functionality for performing data transfer between a local host component and an associated local hardware acceleration component.

FIG. 10 illustrates an example architecture of a host component.

FIG. 11 illustrates an example architecture of management functionality for managing services in a data center.

FIG. 12 illustrates an example architecture with additional components of the management functionality of FIG. 11.

FIGS. 13A-13C illustrate an example architecture for allocating acceleration component functionality to support a service.

FIG. 14 illustrates a flow chart of an example method for allocating acceleration component functionality to support a service.

FIGS. 15A-15D illustrate an example architecture for allocating acceleration component functionality to support services.

DETAILED DESCRIPTION

Examples extend to methods, systems, and computer program products for allocating acceleration component functionality for supporting services. A service manager monitors characteristics of a plurality of hardware acceleration components in a hardware acceleration plane. The hardware acceleration plane provides a configurable fabric of acceleration components for accelerating services.

The service manager allocates a group of interoperating acceleration components, from among the plurality of hardware acceleration components, to provide service acceleration for a service. The group of interoperating acceleration components is allocated based on the monitored characteristics in view of an allocation policy for the hardware acceleration plane. A role at each acceleration component in the group of interoperating acceleration components are linked together to compose a graph providing the service acceleration. The service manager maintains an address for the graph so that the service can request hardware acceleration from the group of interoperating acceleration components.

Implementations may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below. Implementations also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions are computer storage media (devices). Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, implementations of can comprise at least two distinctly different kinds of computer-readable media: computer storage media (devices) and transmission media.

Computer storage media (devices) includes RAM, ROM, EEPROM, CD-ROM, solid state drives (“SSDs”) (e.g., based on RAM), Flash memory, phase-change memory (“PCM”), other types of memory, other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer.

A “network” is defined as one or more data links that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmissions media can include a network and/or data links which can be used to carry desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.

Further, upon reaching various computer system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (devices) (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a “NIC”), and then eventually transferred to computer system RAM and/or to less volatile computer storage media (devices) at a computer system. Thus, it should be understood that computer storage media (devices) can be included in computer system components that also (or even primarily) utilize transmission media.

Computer-executable instructions comprise, for example, instructions and data which, when executed at a processor, cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.

Those skilled in the art will appreciate that the described aspects may be practiced in network computing environments with many types of computer system configurations, including, personal computers, desktop computers, laptop computers, message processors, hand-held devices, wearable devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, watches, routers, switches, and the like. The described aspects may also be practiced in distributed system environments where local and remote computer systems, which are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, both perform tasks. In a distributed system environment, program modules may be located in both local and remote memory storage devices.

The described aspects can also be implemented in cloud computing environments. In this description and the following claims, “cloud computing” is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources. For example, cloud computing can be employed in the marketplace to offer ubiquitous and convenient on-demand access to the shared pool of configurable computing resources. The shared pool of configurable computing resources can be rapidly provisioned via virtualization and released with low management effort or service provider interaction, and then scaled accordingly.

A cloud computing model can be composed of various characteristics such as, for example, on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, and so forth. A cloud computing model can also expose various service models, such as, for example, Software as a Service (“SaaS”), Platform as a Service (“PaaS”), and Infrastructure as a Service (“IaaS”). A cloud computing model can also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, and so forth. In this description and in the claims, a “cloud computing environment” is an environment in which cloud computing is employed.

In this description and the following claims, an “acceleration component” is defined as a hardware component specialized (e.g., configured, possibly through programming) to perform a computing function more efficiently than software running on general-purpose central processing unit (CPU) could perform the computing function. Acceleration components include Field Programmable Gate Arrays (FPGAs), Graphics Processing Units (GPUs), Application Specific Integrated Circuits (ASICs), Erasable and/or Complex programmable logic devices (PLDs), Programmable Array Logic (PAL) devices, Generic Array Logic (GAL) devices, and massively parallel processor array (MPPA) devices.

In this description and in the following claims, a “role” is defined as functionality provided by an acceleration component to a group of interoperating acceleration components used to accelerate a service. Roles at each acceleration component in a group of interoperating acceleration components can be linked together to compose a graph that provides the service acceleration.

In this description and in the following claims, a “graph” is defined as a group of interconnected (e.g., network connected) acceleration components providing acceleration for a service wherein each acceleration component in the group provides a portion of the acceleration functionality.

In this description an in the following claims, an “image” is defined as a file including information that can be used in configuration of an acceleration component, such as, for example, an FPGA. Information included in an image file can be used to program hardware components of an acceleration component (e.g., logic blocks and reconfigurable interconnects of an FPGA) to implement desired functionality. Desired functionality can be implemented to solve virtually any problem which is computable.

In this description and in the following claims, a “neighbor acceleration component” is defined as an acceleration component configured to exchange input and/or output with another acceleration component when interconnected to the other acceleration component within a graph. Neighbor is viewed logically from the perspective of the graph. The physical proximity of an acceleration component relative to another acceleration component is not a determining factor in identifying neighbor acceleration components. That is, acceleration components that are not physically adjacent to one another (or even near to one another on a network or within a datacenter) can be configured to exchange data with one another when interconnected within a graph. Acceleration components interconnected within a graph can be viewed as neighbor acceleration components even if data exchanged between the acceleration components physically passes through other acceleration components outside of the graph or through host components in transit between the acceleration components. However, acceleration components that are physically adjacent or near to one another on a network or in a datacenter and are interconnected within a graph can also be viewed as neighbor acceleration components with respect to one another.

In general, an acceleration component can include an array of programmable logic blocks and hierarchy of reconfigurable interconnects that allow logic blocks to be connected together in different configurations to provide different functionality (i.e., different roles). Image files can be received and loaded at an acceleration component to configure programmable logic blocks and configure interconnects to provide desired functionality (i.e., roles).

In some environments, applications (services) are provided to a client from a data center. A data center includes multiple (and potentially a very large number of) software-driven general purpose computing devices. Each general purpose computing device can include one or more central processing units (CPUs) that process machine-readable instructions to perform specified computing activities. The multiple general purpose computing devices are networked to one another such that the combined power of the multiple general purpose computer systems (or subsets thereof) can be used to perform more complex computing activities.

Data center providers face continuing challenges to increase processing capabilities and efficiency within and provided by data centers. Continuing to add more and more general purpose computing devices is not feasible due at least in part to power limitations. Computing device specialization is one option. For example, computing devices can be specialized for specific scale workloads to provide some efficiency gains. However, computing device specialization is problematic for at least two reasons. First, lack of homogeneity in a data center increases management issues and provides inconsistent platforms for applications to rely on. Further, data center services evolve rapidly, making non-programmable hardware features impractical. Thus, data center providers need continued improvements in performance and efficiency but cannot obtain those improvements from general purpose computing devices.

Aspects facilitate allocating acceleration component functionality for supporting services. A service manager monitors characteristics of a plurality of acceleration components in a hardware acceleration plane. The service manager can monitor acceleration component characteristics, including one or more of: utilization and/or load within the hardware acceleration plane, failures, performance degradation, software errors, machine liveness, service demand (e.g., surges for a particular service), etc. Based on monitored characteristics and in accordance with an allocation policy, the service manager can allocate a group of interoperating acceleration components to accelerate part of a service. In general, the service manager can allocate a group of interoperating acceleration components to facilitate one or more of: balancing load across the plurality of acceleration components, minimizing switching roles at acceleration components, addressing surges in demand for particular services, grouping based on role, grouping based on network bandwidth requirements for a service, grouping for power efficiency, etc.

The service manager can allocate a group of interoperating acceleration components in a variety of different ways. In one aspect, a dedicated group of interoperating acceleration components is configured to accelerate a corresponding service. When the service manager determines a need for additional capacity for accelerating the service, the service manager allocates the corresponding dedicated group of interoperating acceleration components to provide acceleration for the service.

In another aspect, a predetermined pool of acceleration components is available for accelerating services. When the service manager determines a need for additional capacity for accelerating a service, the service manager allocates a group of interoperating acceleration components, from among the predetermined pool, to provide acceleration for the service.

If a further aspect, when the service manager determines a need for additional capacity for accelerating a service, the service manager allocates a group of interoperating acceleration components from the hardware acceleration plane to provide acceleration for the service. Allocation can be in accordance with an allocation policy or possibly random.

In one aspect, one or more groups of interoperating acceleration components are allocated. Each of the one or more groups provides service acceleration for the same service. When subsequently allocating an additional group of interoperating acceleration components, the additional group can provide service acceleration for the same service, can provide service acceleration for a different version of the same service (e.g., document ranking in a different language), or can provide service acceleration for a different service.

Acceleration components can be locally linked to host components (e.g., CPUs), for example, in the same server. When appropriate, a host component can switch roles at locally linked acceleration components. Thus, in an additional aspect, a group of host components locally switches roles at a corresponding group of acceleration components to allocate a group of interoperating acceleration components for accelerating a service.

The service manager can maintain addresses for groups of interoperating acceleration components providing acceleration for different services. In some aspects, an acceleration component provides a role to a group of interoperating acceleration components that provide acceleration of a service. Roles at each acceleration component in the group of interoperating acceleration components are linked together to compose a graph that provides the service acceleration. As such, the service manager can maintain addresses for an acceleration component at the head of each graph.

Switching roles at an acceleration component can vary from full reconfiguration of the acceleration component (loading a new image from DRAM or PCIe) to switching between already programmed functionality. More significant (and more time consuming) reconfiguration may be appropriate when switching between roles for accelerating different services, such as, for example, switching between a document ranking service and a computer vision service. Less significant (and less time consuming) reconfiguration can be possible when switching between roles for accelerating different implementations of similar services, such as, for example, switching between a document ranking service for documents in German and a document ranking service for documents in English. A service manager can minimize reconfiguration as much as possible when allocating a group of interoperating acceleration components to accelerate a service.

In general, a data center deployment includes a hardware acceleration plane and a software plane. The hardware acceleration plane can include a plurality of networked acceleration components (e.g., FPGAs). The software plane can include a plurality of networked software-implemented host components (e.g., central processing units (CPUs)). A network infrastructure can be shared between the hardware acceleration plane and the software plane. In some environments, software-implemented host components are locally linked to corresponding acceleration components.

FIG. 1 illustrates an example architecture 102 that includes a software plane 104 and a hardware acceleration plane 106. The software plane 104 includes a collection of software-driven components (each denoted by the symbol “S”) while the hardware plane includes a collection of hardware acceleration components (each denoted by the symbol “H”). For example, each host component may correspond to a server computer that executes machine-readable instructions using one or more central processing units (CPUs). Each CPU, in turn, may execute the instructions on one or more hardware threads. Each acceleration component can execute hardware logic for implementing functions, such as, for example, portions of services offer by a data center.

Hardware acceleration plane 106 can be constructed using a heterogeneous collection of acceleration components, including different types of acceleration components and/or the same type of acceleration components with different capabilities. For example, hardware acceleration plane 106 can include FPGA devices having different respective processing capabilities and architectures, a mixture of FPGA devices and other devices, and so on. Hardware acceleration plane 106 provides a reconfigurable fabric of acceleration components.

A host component generally performs operations using a temporal execution paradigm (i.e., sequentially) by using each of its CPU hardware threads to execute machine-readable instructions, one after the after. In contrast, an acceleration component may perform operations using a spatial paradigm (i.e., concurrently) by using a large number of parallel logic elements to perform computational tasks. Thus, an acceleration component can perform some operations in less time compared to a software-driven host component. In the context of the architecture 102, the “acceleration” qualifier associated with the term “acceleration component” reflects its potential for accelerating the functions that are performed by the host components.

In one example, architecture 102 corresponds to a data center environment that includes a plurality of computer servers. The computer servers correspond to the host components in the software plane 104. In another example, architecture 102 corresponds to an enterprise system. In a further example, the architecture 102 corresponds to a user device or appliance which uses at least one host component that has access to two or more acceleration components, etc. Other implementations for architecture 102 are also possible.

Common network infrastructure 120 couples host components in the software plane 104 to other host components and couples acceleration components in the hardware acceleration plane 106 to other acceleration components. That is, host components can use common network infrastructure 120 to interact with one another and acceleration components can use common network infrastructure 120 to interact with one another. Interaction among host components in the software plane 104 is independent of the interaction among acceleration components in the hardware acceleration plane 106. As such, two or more acceleration components may communicate in a transparent manner relative to host components in the software plane 104, outside the direction of the host components, and without the host components being “aware” of particular interaction is even taking place in the hardware acceleration plane 106.

Architecture 102 can use any of a variety of different protocols to facilitate communication between acceleration components over network infrastructure 120 and can use any of a variety of different protocols to facilitate communication between host components over network infrastructure 120. For example, architecture 102 can uses Ethernet protocol to transmit Internet Protocol (IP) packets over network infrastructure 120. In one implementation, each local host component in a server is given a single physical IP address. The local acceleration component in the same server may adopt the same IP address. The server can determine whether an incoming packet is destined for the local host component or destined for the local acceleration component in different ways. For example, packets that are destined for the local acceleration component can be formulated as UDP packets having a specific port; host-defined packets, on the other hand, may not be formulated in this way. In another example, packets belonging to the acceleration plane 106 can be distinguished from packets belonging to the software plane 104 based on the value of a status flag in each of the packets.

As such, architecture 102 can be viewed as two logical networks (software plane 104 and hardware acceleration plane 106) that share the same physical network communication links. Packets associated with the two logical networks may be distinguished from each other by their respective traffic classes.

In another aspect, each host component in the architecture 102 is coupled to at least one acceleration component in hardware acceleration plane 104 through a local link. For example, a host component and acceleration component can be arranged together and maintained as single serviceable unit (e.g., a server) within architecture 102. In this arrangement, the server can be referred to as the “local” host component to distinguish it from other host components that are associated with other servers. Similarly, acceleration component(s) of a server can be referred to as the “local” acceleration component(s) to distinguish them from other acceleration components that are associated with other servers.

As depicted in architecture 102, host component 108 is coupled to acceleration component 110 through a local link 112 (e.g., a Peripheral Component Interconnect Express (PCIe) link). Thus, host component 108 is a local host component form the perspective of acceleration component 110 and acceleration component 110 is a local acceleration component from the perspective of host component 108. The local linking of host component 108 and acceleration component 110 can form part of a server. More generally, host components in software plane 104 can be locally coupled to acceleration components in hardware acceleration plane 106 through many individual links collectively represented as a local_(H)-to-local_(S) coupling 114.

Thus, a host component can interact directly with any locally linked acceleration components. As such, a host component can initiate communication to a locally linked acceleration component to cause further communication among multiple acceleration components. For example, a host component can issue a request for a service (or portion thereof) where functionality for the service (or portion thereof) is composed across a group of one or more acceleration components in hardware acceleration plane 106.

Thus, a host component can also interact indirectly with other acceleration components in hardware acceleration plane 106 to which the host component is not locally linked. For example, host component 108 can indirectly communicate with acceleration component 116 via acceleration component 110. More specifically, acceleration component 110 communicates with acceleration component 116 via a link 118 (e.g., network infrastructure 120).

Acceleration components in hardware acceleration plane 106 can be used to accelerate larger-scale services robustly in a data center. Substantial portions of complex datacenter services can be mapped to acceleration components (e.g., FPGAs) by using low latency interconnects for computations spanning multiple acceleration components. Acceleration components can also be reconfigured as appropriate to provide different service functionality at different times.

FIG. 2 illustrates an example architecture 202 that can be used in a data center. Servers 204, 206, and 208 can be included in a rack in the data center. Each of servers 204, 206, and 208 can be coupled to top-of-rack (TOR) switch 210. Other racks, although not shown, may have a similar configuration. Server 204 further includes host component 212 including CPUs 214, 216, etc. Host component 212 along with host components from servers 206 and 208 can be included in software plane 104. Server 204 also includes acceleration component 218. Acceleration component 218 along with acceleration components from servers 206 and 208 can be included in hardware acceleration plane 106.

Acceleration component 218 is directly coupled to host component 212 via local link 220 (e.g., a PCIe link). Thus, host component 212 can view acceleration component 218 as a local acceleration component and acceleration component 218 can view host component 212 as a local host component. Acceleration component 218 and host component 212 are also indirectly coupled by way of network interface controller 222 (e.g., used to communicate across network infrastructure 120). Server 204 can load images representing service functionality onto acceleration component 218.

Acceleration component 218 is also coupled to TOR switch 210. Hence, in architecture 202, acceleration component 218 represents the path through which host component 212 interacts with other components in the data center (including other host components and other acceleration components). Architecture 202 allows acceleration component 218 to perform processing on packets that are received from (and/or sent to) TOR switch 210 (e.g., by performing encryption, compression, etc.), without burdening the CPU-based operations performed by host component 212.

Management functionality 232 serves to manage the operations of architecture 202. Management functionality 232 can be physically implemented using different control architectures. For example, in one control architecture, the management functionality 232 may include plural local management components that are coupled to one or more global management components.

FIG. 3 illustrates an example server 302. Server 302 includes host component 304 including CPUs 306, 308, etc., acceleration component 310, and local link 312. Acceleration component 310 is directly coupled to host component 304 via local link 312 (e.g., a PCIe link). Thus, host component 304 can view acceleration component 310 as a local acceleration component and acceleration component 310 can view host component 304 as a local host component. Host component 304 and acceleration component 310 can be included in software plane 104 and hardware acceleration plane 106 respectively. Server 302 implements network interface controller (NIC) 314 as an internal component of acceleration component 310. Server 302 can load images representing service functionality onto acceleration component 310.

FIG. 4 illustrates an example server 402. Server 402 includes host components 404 through 406 including any number n of host components. Host components 404 through 406 can be included in software plane 104. Server 402 includes acceleration components 408 through 410 including any number m of acceleration components. Acceleration components 408 through 410 can be included in hardware acceleration plane 106. Server 402 can also include a network interface controller (not shown).

Server 402 can include a single host component locally linked to two acceleration components. The two acceleration components can perform different respective tasks. For example, one acceleration component can be used to process outgoing traffic to its local TOR switch, while the other acceleration component can be used to process incoming traffic from the TOR switch. In addition, server 402 can load images representing service functionality onto any of the acceleration components 408 through 410.

In general, a service (e.g., search ranking, encryption, compression, computer vision, speech translation, etc.) can be implemented at one or more host components, at one or more acceleration components, or a combination of one or more host components and one or more acceleration components depending on what components are better suited to provide different portions of the service.

FIG. 5 illustrates an example service 512 implemented using components of software plane 104 and components of hardware acceleration plane 106. In operation (1), host component 502 communicates with host component 504 in the course of performing a computational task. In operation (2) host component 504 then requests the use of service 512 that is implemented in the hardware acceleration plane 106 (although host component 504 may not be “aware” of where service 512 is implemented) by communicating with acceleration component 506 over a local link.

The requested service 512 is a composed service spread out over a plurality of acceleration components, each of which performs a specified portion of the service. Although acceleration component 506 was contacted to request use of the service 512, acceleration component 506 may not be the head of the composed service (or even be part of the multi-component service). Instead, acceleration component 508 may be the head component for the composed service.

As such, in operation (3), host component 504 indirectly communicates with acceleration component 508 via acceleration component 506. Acceleration component 508 then performs its portion of the composed service to generate an intermediate output result. In operation (4), acceleration component 508 then invokes acceleration component 510, which performs another respective portion of the composed service, to generate a final result. In operations (5), (6), and (7), the hardware acceleration plane 106 successively forwards the final result back to the requesting host component 504, through the same chain of components set forth above but in the opposite direction.

Operations in hardware acceleration plane 106 are performed in an independent manner of operations performed in the software plane 104. In other words, the host components in the software plane 104 do not manage the operations in the hardware acceleration plane 106. However, the host components may invoke the operations in the hardware acceleration plane 106 by issuing requests for services that are hosted by the hardware acceleration plane 106.

The hardware acceleration plane 106 operates in a manner that is transparent to a requesting host component. For example, host component 504 may be “unaware” of how its request is being processed in hardware acceleration plane 106, including the fact that the service corresponds to a composed service.

Communication in software plane 104 (e.g., corresponding to operation (1)) can take place using the same common network infrastructure 120 as communication in the hardware acceleration plane 106 (e.g., correspond to operations (3)-(6)). Operations (2) and (7) may take place over a local link, corresponding to the local_(H)-to-local_(S) coupling 114 shown in FIG. 1.

FIG. 6 illustrates an example service 612 implemented using components of a software plane and components of hardware acceleration plane 106 Service 612 uses a different flow structure than service 512. More specifically, in operation (1), a host component (not shown) sends a request to its local acceleration component 602. In this example, local acceleration component 602 is also the head component of service 612. In operation (2), local acceleration component 602 may then forward one or more messages to a plurality of respective acceleration components. Each acceleration component that receives a message may perform a portion of a composed service in parallel with the other acceleration components. (FIG. 6 may represent only a portion of service 612, other portions of service 612 can be implemented at other hardware accelerators).

In general, an acceleration component can include any of variety of components some of which can be more or less common across different application images. Some components, such as, for example, a role, are distinct between application images. Other components, such as, for example, routers, transport components, switches, diagnostic recorders, etc., can be relatively common between some number of application images. These other relatively common components can be viewed as being included in an intermediate layer of abstraction or “soft shell”. Further components, such as, for example, bridges, bypass controls, Network Interface Cards, Top of Rack Interfaces, buffers, memory controllers, PCIe controllers, Inter-FPGA network controllers, configuration memories and interfaces, host interfaces, debugging and back-channel interfaces (e.g., Joint Test Action Group (JTAG) interfaces, Inter-Integrated Circuit (I2C) interfaces, etc.), sensors, etc. can be very common between a higher number of (and essentially all) application images. These further very common components can be viewed as included in a greater layer of abstraction (e.g., than the other relatively common components) or “shell”.

When an FPGA is reconfigured with new functionality, it is likely (although not guaranteed) that a role (i.e., the application-specific logic) at the FGPA is changed. However, it is unlikely that existing functionality in the soft shell is changed and it is extremely unlikely that existing functionality in the soft shell is changed. Thus, components in the soft shell and to greater extent components in the shell provide a common interface for a role. As such, the shell allows code for a role to be ported relatively easy across different acceleration components.

Turning to FIG. 7, FIG. 7 illustrates an example architecture of an acceleration component 702. Acceleration component 702 can be included in hardware acceleration plane 106. Components included in acceleration component 702 can be implemented on hardware resources (e.g., logic blocks and programmable interconnects) of acceleration component 702.

Acceleration component 702 includes application logic 706, soft shell 704 associated with a first set of resources and shell 711 associated with a second set of resources. The resources associated with shell 711 correspond to lower-level interface-related components that generally remain the same across many different application scenarios. The resources associated with soft shell 704 can remain the same across at least some different application scenarios. Application logic 706 may be further conceptualized as including an application domain (e.g., a “role”). The application domain or role can represent a portion of functionality included in a composed service spread out over a plurality of acceleration components.

The application domain hosts application logic 706 that performs service specific tasks (such as a portion of functionality for ranking documents, encrypting data, compressing data, facilitating computer vision, facilitating speech translation, machine learning, etc.). Resources associated with soft shell 704 are generally less subject to change compared to the application resources, and the resources associated with shell 711 are less subject to change compared to the resources associated with soft shell 704 (although it is possible to change (reconfigure) any component of acceleration component 702).

In operation, application logic 706 interacts with the shell resources and soft shell resources in a manner analogous to the way a software-implemented application interacts with its underlying operating system resources. From an application development standpoint, the use of common shell resources and soft shell resources frees a developer from having to recreate these common components for each service.

Referring first to shell 711, shell resources include bridge 708 for coupling acceleration component 702 to the network interface controller (via a NIC interface 710) and a local top-of-rack switch (via a TOR interface 712). Bridge 708 also includes a data path that allows traffic from the NIC or TOR to flow into acceleration component 702, and traffic from the acceleration component 702 to flow out to the NIC or TOR. Internally, bridge 708 may be composed of various FIFOs (714, 716) which buffer received packets, and various selectors and arbitration logic which route packets to their desired destinations. A bypass control component 718, when activated, can control bridge 708 so that packets are transmitted between the NIC and TOR without further processing by the acceleration component 702.

Memory controller 720 governs interaction between the acceleration component 702 and local memory 722 (such as DRAM memory). The memory controller 720 may perform error correction as part of its services.

Host interface 724 provides functionality that enables acceleration component 702 to interact with a local host component (not shown). In one implementation, the host interface 724 may use Peripheral Component Interconnect Express (PCIe), in conjunction with direct memory access (DMA), to exchange information with the local host component. The outer shell may also include various other features 726, such as clock signal generators, status LEDs, error correction functionality, and so on.

Turning to soft shell 704, router 728 is for routing messages between various internal components of the acceleration component 702, and between the acceleration component and external entities (e.g., via a transport component 730). Each such endpoint is associated with a respective port. For example, router 728 is coupled to memory controller 720, host interface 724, application logic 706, and transport component 730.

Transport component 730 formulates packets for transmission to remote entities (such as other acceleration components), and receives packets from the remote entities (such as other acceleration components). A 3-port switch 732, when activated, takes over the function of the bridge 708 by routing packets between the NIC and TOR, and between the NIC or TOR and a local port associated with the acceleration component 702.

Diagnostic recorder 734 can store information regarding operations performed by the router 728, transport component 730, and 3-port switch 732 in a circular buffer. For example, the information may include data about a packet's origin and destination IP addresses, host-specific data, timestamps, etc. A technician may study a log of the information in an attempt to diagnose causes of failure or sub-optimal performance in the acceleration component 702.

A plurality of acceleration components similar to acceleration component 702 can be included in hardware acceleration plane 106.

Acceleration components can use different network topologies (instead of using common network infrastructure 120 for communication) to communicate with one another. In one aspect, acceleration components are connected directly to one another, such as, for example, in a two dimensional torus.

FIG. 8 illustrates an acceleration component 802 including separate configurable domains 804, 806, etc. A configuration component (not shown) can configure each configurable domain without affecting other configurable domains. Hence, the configuration component can configure one or more configurable domains while the other configurable domains are executing operations based on their respective configurations, which are not disturbed.

FIG. 9 illustrates functionality for performing data transfer between a host component 902 and an associated (e.g., locally linked) acceleration component 904. Data can be transferred via a host interface (e.g., host interface 724), for example, using PCIe in conjunction with DMA memory transfer). In operation (1), host logic 906 places data to be processed into kernel-pinned input buffer 908 in main memory associated with the host logic 906. In operation (2), the host logic 906 instructs the acceleration component 904 to retrieve the data and begin processing it. The host logic's thread is then either put to sleep until it receives a notification event from the acceleration component 904, or it continues processing other data asynchronously. In operation (3), the acceleration component 904 transfers the data from the host logic's memory and places it in an acceleration component input buffer 910.

In operations (4) and (5), the application logic 912 retrieves the data from the input buffer 910, processes it to generate an output result, and places the output result in an output buffer 914. In operation (6), the acceleration component 904 copies the contents of the output buffer 914 into output buffer 916 (in the host logic's memory). In operation (7), acceleration component 904 notifies the host logic 906 that the data is ready for it to retrieve. In operation (8), the host logic thread wakes up and consumes the data in the output buffer 916. Host logic 906 may then discard the contents of the output buffer 916, which allows the acceleration component 904 to reuse it in the next loading operation.

FIG. 10 illustrates an example architecture of a host component 1002. Host component 1002 can include one or more processing devices 1004, such as one or more central processing units (CPUs). Host component 1002 can also include any storage resources 1006 for storing any kind of information, such as code, settings, data, etc. Without limitation, for instance, storage resources 1006 may include any of RAM of any type(s), ROM of any type(s), flash devices, hard disks, optical disks, and so on. More generally, any storage resource can use any technology for storing information. Further, any storage resource may provide volatile or non-volatile retention of information. Further, any storage resource may represent a fixed or removable component of host component 1002. In one case, host component 1002 may perform any of the operations associated with local tenant functionality when processing devices 1004 carry out associated instructions stored in any storage resource or combination of storage resources. Host component 1002 also includes one or more drive mechanisms 1008 for interacting with any storage resource, such as a hard disk drive mechanism, an optical disk drive mechanism, and so on.

Host component 1002 also includes an input/output module 1010 for receiving various inputs (via input devices 1012), and for providing various outputs (via output devices 1014). One particular output mechanism may include a presentation device 1016 and an associated graphical user interface (GUI) 1018. Host component 1002 can also include one or more network interfaces 1020 for exchanging data with other devices via one or more communication conduits 1022. One or more communication buses 1024 communicatively couple the above-described components together.

Communication conduit(s) 1022 can be implemented in any manner, e.g., by a local area network, a wide area network (e.g., the Internet), point-to-point connections, etc., or any combination thereof. Communication conduit(s) 1022 can include any combination of hardwired links, wireless links, routers, gateway functionality, name servers, etc., governed by any protocol or combination of protocols.

A plurality of host components similar to host component 1002 can be included in software plane 104.

FIG. 11 illustrates an example architecture 1102 of management functionality 1122 for managing services in a data center. Architecture 1102 can be included in architecture 102. As such, management functionality 1122 as well as other associated components can be implemented on hardware resources of a host component (e.g., in software plane 104) and/or implemented on hardware resources of an acceleration component (e.g., in hardware acceleration plane 106). Host component hardware resources can include any of the hardware resources associated with host component 1002. Acceleration component hardware resources can include any of the hardware resources associated with acceleration component 702.

Management functionality 1122 can include a number of sub-components that perform different respective functions (which can be physically implemented in different ways). A local determination component 1124, for example, can identify the current locations of services within architecture 102, based on information stored in a data store 1126. In operation, location determination component 1124 may receive a request for a service. In response, location determination component 1124 returns an address associated with the service, if that address is present in data store 1126. The address may identify a particular acceleration component in hardware acceleration plane 106 that hosts (or is the head of) the requested service.

Request handling component (RHC) 1128 processes requests for services made by instances of tenant functionality. For example, an instance of tenant functionality may correspond to a software program running on a particular local host component. That software program may request a service in the course of its execution. The RHC 1128 handles the request by determining an appropriate component in architecture 102 to provide the service. Possible components for consideration include: a local acceleration component (associated with the local host component from which the request originated); a remote acceleration component; and/or the local host component itself (whereupon the local host component implements the service in software). RHC 1128 makes its determinations based on one or more request handling considerations, such as whether the requested service pertains to a line-rate service. Further, the RHC 1128 may interact with the location determination component 1124 in performing its functions.

A global service allocation component (GSAC) 1130 can operate in a background and global mode, allocating services to acceleration components based on global conditions in architecture 102 (rather than handling individual requests from instances of tenant functionality, as does RHC 1128). For example, GSAC 1130 may invoke its allocation function in response to a change in demand that affects one or more services. GSAC 1130 makes its determinations based on one or more allocation considerations, such as the historical demand associated with the services, etc. Further, the GSAC 1130 may interact with the location determination component 1124 in performing its functions. A sub-component of GSAC 1130 can also manage multi-component and/or composed services. A multi-component service is a service that is composed of plural parts. Plural respective acceleration components perform the respective parts.

FIG. 12 illustrates an example architecture with additional components of management functionality 1122. As described, location determination component 1124 identifies the current location of services within architecture 102, based on information stored in the data store 1126. In operation, the location determination component 1124 receives a request for a service. In response, it returns the address of the service, if present within the data store 1126. The address may identify a particular acceleration component that implements the service.

Request handling component (RHC) 1128 handles requests for services by tenant functionality that resides on the host components. In response to each request by a local host component, RHC 1128 determines an appropriate component to implement the service. For example, RHC 1128 may choose from among: a local acceleration component (associated with the local host component that made the request), a remote acceleration component, or the local host component itself (whereupon the local host component will implement the service in software), or some combination thereof. RHC 1128 performs its determinations based on one or more request handling considerations.

General allocation component (GSAC) 1130, on the other hand, operates by globally allocating services to acceleration components within architecture 102 to meet overall anticipated demand in the data processing system and/or to satisfy other objectives (rather than individual requests by host components). In performing its functions, the GSAC component 1130 may draw on a data store 1202 that provides free pool information. The free pool information identifies acceleration components that have free capacity to implement one or more services. The GSAC 1130 can also receive input information that has a bearing on its allocation decisions. One such piece of input information pertains to historical demand information associated with a service, e.g., as maintained in a data store 1204.

GSAC 1130 and RHC 1128 may use, in part, common logic in reaching their allocation decisions, and that common logic may, in part, taken into account similar allocation considerations. Further, both RHC 1128 and GSAC 1130 interact with the location determination component 124 in the course of performing their respective operations. Otherwise, as described, the GSAC 1130 frames its decisions in a global context, whereas the RHC 1128 is an on-demand component that is primarily focused on satisfying specific requests.

Configuration component 1206 configures acceleration components, e.g., by sending a configuration steam to the acceleration components. A configuration stream specifies the logic (e.g., an image) to be “programmed” into a recipient acceleration component. The configuration component 1206 may use different strategies to configure an acceleration component.

The failure monitoring component 1208 determines whether a previously configured acceleration component has failed. Various components of the management functionality 1122 may respond to failure notification by substituting a spare acceleration component for a failed acceleration component, reconfiguring an acceleration component, partial reconfiguring acceleration component, reloading data in an acceleration component, etc.

As described, functionality for a service or portion thereof can be provided by linking roles from a group of interoperating acceleration components. The linked roles can be composed in a directed graph in any variety of different ways, including a directed acyclic graph, a directed cyclic graph, etc., to provide service functionality and/or acceleration. For example, in some aspects, linked roles are composed in a pipeline or ring.

FIGS. 13A and 13B illustrate an example architecture 1300 for allocating acceleration component functionality to support a service. Referring initially to FIG. 13A, computer architecture 1300 includes service manager 1321. Service manager 1321 can be connected to (or be part of) network infrastructure 120, such as, for example, a Local Area Network (“LAN”), a Wide Area Network (“WAN”), and even the Internet. Accordingly, service manager 1321, host components in software plane 104, acceleration components in hardware acceleration plane 106 and any other connected computer systems and their components, can create message related data and exchange message related data (e.g., Internet Protocol (“IP”) datagrams and other higher layer protocols that utilize IP datagrams, such as, Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”), Simple Object Access Protocol (SOAP), etc. or using other non-datagram protocols) over network infrastructure 120.

In general, configuration service 1321 is configured to monitor network infrastructure 120 and allocate groups of interoperating acceleration components in hardware acceleration plane 106 to accelerate services. Configuration service 1321 can include any of the functionality described with respect to management functionality 232 and management functionality 1122.

Turning to FIG. 14, FIG. 14 illustrates a flow chart of an example method 1400 for allocating acceleration component functionality to support a service. Method 1400 will be described with respect to the components and data of architecture 1300.

Method 1400 includes monitoring characteristics of a plurality of hardware acceleration components in a hardware acceleration plane, the hardware acceleration plane providing a configurable fabric of acceleration components for accelerating services (1401). For example, service manager 1321 can monitor the characteristics of acceleration components in hardware acceleration plane 106. Within hardware acceleration plane 106, service manager 1321 can monitor one or more of: load, utilization, failures, machine liveness, and service demand.

Method 1400 includes allocating a group of interoperating acceleration components, from among the plurality of hardware acceleration components, to provide service acceleration for a service, the group of interoperating acceleration components allocated based on the monitored characteristics in view of an allocation policy for the hardware acceleration plane, a role at each acceleration component in the group of interoperating acceleration components linked together to compose a graph providing the service acceleration (1402). For example, service manager 1321 (e.g., using global service allocation component (GSAC) 1130 or another similar component) can allocate acceleration components 1301, 1302, 1303, and 1304 to provide acceleration for a service based on monitored characteristics of hardware acceleration plane 104 and in view of allocation policy 1326. Allocation policy 1326 can be defined to facilitate one or more of: balancing load across acceleration components in hardware acceleration plane 106, minimizing switching of roles at acceleration components in hardware acceleration plane 106, addressing changes for demand in service acceleration, minimizing communication latency between acceleration components in hardware acceleration plane 106 (e.g., by selecting physical adjacent acceleration components), grouping based on role, grouping based on network bandwidth requirements for a service, grouping for power efficiency, etc. A role at each of acceleration components 1301, 1302, 1303, and 1304 can be linked together to compose graph 1322.

Method 1400 includes maintaining an address for the graph so that the service can request hardware acceleration from the group of interoperating acceleration components (1403). For example, service manager 1321 can maintain address 1327 for acceleration component 1301 (the head of graph 1322) in storage 1351. Thus, when service manager 1321 receives a subsequent request for service acceleration that can be satisfied by graph 1322, service manager 1321 can use address 1327 to direct the request to graph 1322.

Turning to FIG. 13B, FIG. 13B depicts a more detailed view of graph 1322. As depicted, graph 1322 includes acceleration components 1301, 1302, 1303, and 1304. Acceleration components 1301, 1302, 1303, and 1304 can be FPGAs. The depicted arrangement of acceleration components 1301, 1302, 1303, and 1304 is logical. The physical proximity of acceleration components 1301, 1302, 1303, and 1304 relative to one another can vary (e.g., same server, different servers same rack, different racks, etc.).

Acceleration components 1301, 1302, 1303, and 1304 are programmed with corresponding roles 1311, 1312, 1313, and 1314 respectively. Roles 1311, 1312, 1313, and 1314 are linked to one another to compose graph 1322. Graph 1322 can provide hardware acceleration for a service.

Input and output from roles at (logically) neighboring acceleration components may depend on one another or input and output from other components (e.g., host components or functionality composed from a different group of interoperating acceleration components). For example, input to role 1312 can depend on output from role 1311. Similarly, input to role 1313 can depend on output from role 1312.

Some or all of acceleration components 1301, 1302, 1303, and 1304 can participate in one-way or two-way communication with (logically) neighboring acceleration components and other components (e.g., host components). Thus, input and output from one acceleration component can depend on input and output from another acceleration component and vice versa. For example, input to role 1311 can depend on output from role 1312 and input to role 1312 can depend on output from role 1313.

A graph can be composed from a linked roles at a group of interoperating acceleration components. For example, graph 1322 can provide acceleration for part of a document ranking service used to provide search engine results. Graph 1322 can interoperate with other portions of service functionality composed from other groups of interoperating acceleration components and/or provided by one or more host components. For example, for a document ranking service, document feature extraction can be composed from one group of interoperating acceleration components, free form expression calculations can be composed from another group of interoperating acceleration components, and scoring calculations can be composed from a further group of interoperating acceleration components.

Thus, other graphs in hardware acceleration plane 106 can provide acceleration for another part of the document ranking service or can provide acceleration for some other service (e.g., encryption, compression, computer vision, speech translation, etc.).

Service manager 1321 can monitor the performance of graph 1322. Service manager 1321 can consider the performance of graph 1322 when allocating groups of interoperating acceleration components for accelerating other parts of a service and for accelerating other services. For example, if service manager 1321 detects an error in graph 1322, service manager may need to allocate a different group of interoperating acceleration components to provide graph 1322.

In response, service manage 1321 can send a halt command to graph 1322. The halt command halts operation of one or more of roles 1311, 1312, 1313, and 1314 as well as quiescing graph 1322. Quiescing graph 1322 stops all network traffic flowing into and out of graph 1322. A halt command can also instructs roles within graph 1322 to ignore any data coming out of other roles in graph 1322.

When appropriate, service manager 1321 can also notify upstream and downstream components of roles (e.g., in the same graph) that another role is being halted. Upstream and downstream components can then take appropriate actions with in-process data (e.g., buffer, drop, send NACKs to other components, etc.) until the role is again operational.

Turning to FIG. 13C, service 1341 can use address 1327 to determine that acceleration component 1301 is the head of graph 1322. Service 1341 can send acceleration request 1342 to acceleration component 1301. Acceleration request 1342 can be a request to process data 1343 (e.g., a set of documents for document ranking). Data 1343 can be processed by roles 1311, 1312, 1313, and 1314 (and possibly passed off to and returned from other acceleration components) to formulate results 1344 (a set of ranked documents). Results 1344 can be returned back to service 1341.

In general, an acceleration component (e.g., 1301, 1302, 1303, 1304, etc.) can include an array of programmable logic blocks and a hierarchy of reconfigurable interconnects that allow logic blocks to be connected together in different configurations (to provide different functionality (i.e., different roles)). Image files can be loaded at an acceleration component to configure programmable logic blocks and configure interconnects to provide desired functionality. Images can be stored at a network location and/or local to an acceleration component or locally linked host component.

FIGS. 15A-15D illustrate an example architecture for allocating acceleration component functionality to support services. Referring initially to FIG. 15A, computer architecture 1500 includes service manager 1521. Service manager 1521 can be connected to (or be part of) network infrastructure 120, such as, for example, a Local Area Network (“LAN”), a Wide Area Network (“WAN”), and even the Internet. Accordingly, service manager 1521, host components in software plane 104, acceleration components in hardware acceleration plane 106 and any other connected computer systems and their components, can create message related data and exchange message related data (e.g., Internet Protocol (“IP”) datagrams and other higher layer protocols that utilize IP datagrams, such as, Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”), Simple Object Access Protocol (SOAP), etc. or using other non-datagram protocols) over network infrastructure 120.

Hardware acceleration plane 106 includes a finite number of acceleration components. Service manager 1521 can allocate the finite number of acceleration components to compose various different graphs for accelerating services. Service manager 1521 can monitor characteristics of network infrastructure 120. Service manager 1521 can allocate groups of interoperating acceleration components to compose graphs based on the monitored characteristics and in view of allocation policy 1526.

In general, configuration service 1521 is configured to monitor network infrastructure 120 and allocate groups of interoperating acceleration components in hardware acceleration plane 106 to accelerate services. Configuration service 1521 can include any of the functionality described with respect to management functionality 232 and management functionality 1122.

As depicted in FIG. 15A, acceleration components in hardware acceleration plane 106 are allocated to compose a copy of graph 1501, a copy of graph 1502, two copies of graph 1503, and a copy of graph 1504. Addresses 1527, 1528, etc. stored in storage 1541 can be used to direct requests for acceleration to the appropriate graphs.

During continued monitoring, service manager 1521 can detect an increased demand for graph 1502. Based on the current allocation of acceleration components in hardware plane 106 and in view of allocation policy 1526, service manager 1521 can (re)allocate acceleration components to meet the increased demand for graph 1502. Service manager 1521 can (re)allocate acceleration components in a manner that complies to an extent possible with allocation policy 1526 (e.g., balances load in hardware acceleration plane 106, minimize role switching, etc.).

Turning to FIG. 15B, in one aspect, service manager 1521 allocates unused (spare) acceleration components to compose another copy of graph 1502. Addresses in storage 1541 can be adjusted so that the other copy of graph 1502 can be accessed.

Turning to FIG. 15C, in another aspect, service manager 1521 reconfigures (e.g., loads images files at) a group of interoperating acceleration components to compose together another copy of graph 1502. Reconfiguration removes graph 1501. There may be so little demand for graph 1501 that requests for graph 1501 can be temporarily queued up until another copy of graph 1501 can be allocated elsewhere in hardware plane 106. Addresses in storage 1541 can be adjusted so that the other copy of graph 1502 can be accessed and so that reference to graph 1501 is removed.

Turning to FIG. 15D, in another aspect, service manager 1521 changes a group of interoperating acceleration components composed to provide graph 1503 into a group of interoperating acceleration components composed to provide graph 1502. The group of interoperating acceleration components can be configured with roles for providing both graph 1502 and graph 1503. Service manager 1521 can send configuration data to change the roles from providing graph 1503 to providing graph 1502. Configuration data can used to switch between roles (or otherwise change behavior) at an acceleration component using the same underlying image. As such, roles (or other behavior) can be changed without having to load a new image file. Addresses in storage 1541 can be adjusted so that the other copy of graph 1502 can be accessed and so that just the remaining copy of graph of 1503 can be accessed.

The graphs in FIGS. 15A-15D can be for accelerating completely different services, such as, for example, document ranking, data encryption, data compression, speech translation, and computer vision. In another aspect, some of the graphs in FIGS. 15A-15D can be for accelerating different types of similar or even the same service. For example, graph 1502 can be for accelerating document ranking for documents in French and graph 1503 can be for accelerating document ranking for documents in English. Graphs 1501 and 1504 can be for accelerating other different services.

In one aspect, service manager 1521 allocates a plurality of graphs of the same type (kind) and then balances load between the plurality of graphs. For example, service manager 1521 can allocate two graphs 1502 for accelerating ranking documents in French. Service manager 1521 (e.g., using request handling component (RHC) 1128 or another similar component) can then route requests for ranking documents in French between the two graphs 1502 based on any the described monitored characteristics and in accordance with any of the described allocation policies.

In general, the described aspects are advantageous for using a finite number of acceleration components to accelerate services. Acceleration components can be allocated in a manner that balances load in a hardware acceleration plane, minimizing role switching, and adapts to demand changes. When role switching is appropriate, lower overhead mechanisms (e.g., configuration data) can be used to switch roles to the extent possible.

In some aspects, a system includes a hardware acceleration plane, a software plane, and a network infrastructure. The hardware acceleration plane includes a configurable fabric of a plurality of acceleration components (e.g., hardware accelerators, such as, FPGAs). The software plane includes a plurality of host components (e.g., CPUs) running software. The network infrastructure is shared by acceleration components in the hardware acceleration plane and host components in the software plane. The network infrastructure is used by acceleration components to communicate directly with one another. Local links connect acceleration components and host components (e.g., in the same server).

The system also includes one or more computer storage devices having stored thereon computer-executable instructions representing a service manager. The service manager is configured to allocate acceleration component functionality for supporting a service. Allocating acceleration component functionality includes monitoring characteristics of the plurality of hardware acceleration components.

Allocating acceleration component functionality includes allocating a group of interoperating acceleration components, from among the plurality of hardware acceleration components, to provide service acceleration for a service. The group of interoperating acceleration components is allocated based on the monitored characteristics in view of an allocation policy for the hardware acceleration plane. A role at each acceleration component in the group of interoperating acceleration components linked together to compose a graph providing the service acceleration. Allocating acceleration component functionality includes maintaining an address for the graph so that the service can request hardware acceleration from the group of interoperating acceleration components.

In another aspect, a method for allocating acceleration component functionality for supporting a service. Characteristics of the plurality of hardware acceleration components are monitored. The hardware acceleration plane provides a configurable fabric of acceleration components for accelerating services.

A group of interoperating acceleration components, from among the plurality of hardware acceleration components, is allocated to provide service acceleration for a service. The group of interoperating acceleration components is allocated based on the monitored characteristics in view of an allocation policy for the hardware acceleration plane. A role at each acceleration component in the group of interoperating acceleration components linked together to compose a graph providing the service acceleration. An address for the graph is maintained so that the service can request hardware acceleration from the group of interoperating acceleration components.

In another aspect, a computer program product for use at a computer system includes one or more computer storage devices having stored thereon computer-executable instructions that, in response to execution at a processor, cause the computer system to implement a method for allocating acceleration component functionality for supporting a service.

The computer program product includes computer-executable instructions that, in response to execution at a processor, monitor characteristics of a plurality of hardware acceleration components in a hardware acceleration plane. The hardware acceleration plane provides a configurable fabric of acceleration components for accelerating services.

The computer program product includes computer-executable instructions that, in response to execution at a processor, allocate a group of interoperating acceleration components, from among the plurality of hardware acceleration components, to provide service acceleration for a service. The group of interoperating acceleration components is allocated based on the monitored characteristics in view of an allocation policy for the hardware acceleration plane. A role at each acceleration component in the group of interoperating acceleration components is linked together to compose a graph providing the service acceleration. The computer program product includes computer-executable instructions that, in response to execution at processor, maintain an address for the graph so that the service can request hardware acceleration from the group of interoperating acceleration components.

The present described aspects may be implemented in other specific forms without departing from its spirit or essential characteristics. The described aspects are to be considered in all respects only as illustrative and not restrictive. The scope is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope. 

What is claimed:
 1. A method in a data center comprising a plurality of servers interconnected via a network, wherein each of the plurality of servers comprises at least one acceleration component, wherein the at least one acceleration component comprises a plurality of hardware logic blocks interconnected using reconfigurable interconnects, the method comprising: linking a first set of acceleration components corresponding to a first set of the plurality of the servers into a first graph configured to accelerate a first service, wherein each of the first set of acceleration components is programmed to perform any of a first set of roles corresponding to the first service; linking a second set of acceleration components corresponding to a second set of the plurality of the servers into a second graph configured to accelerate a second service, different from the first service, wherein each of the second set of acceleration components is programmed to perform any of a second set of roles corresponding to the second service; maintaining in a storage a first address for the first graph such that the first service can request hardware acceleration from the first set of acceleration components; maintaining in the storage a second address for the second graph such that the second service can request hardware acceleration form the second set of acceleration components; and in response to an increased demand for hardware acceleration from the second graph, based on an allocation policy, a service manager comprising computer-executable instructions: (1) switching, using configuration data and without loading a new image file, at least one of the first set of acceleration components from performing any of the first set of roles to performing any of the second set of roles, and (2) adjusting at least one of the first address or the second address.
 2. The method of claim 1, wherein the first service is a service selected from among: document ranking, data encryption, data compression, speech translation, and computer vision.
 3. The method of claim 1, wherein the at least one acceleration component comprises at least one Field Programmable Gate Array (FPGA).
 4. The method of claim 1, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate balancing load across the hardware plane.
 5. The method of claim 1, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate minimizing switching of roles among acceleration components in the hardware plane.
 6. The method of claim 1, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate minimizing communication latency between acceleration components in the hardware plane.
 7. The method of claim 1, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the service manager is configured to monitor machine liveness of acceleration components in the hardware plane.
 8. A system, in a data center comprising a plurality of servers interconnected via a network, wherein each of the plurality of servers comprises at least one acceleration component, wherein the acceleration component comprises a plurality of hardware logic blocks interconnected using reconfigurable interconnects, the system comprising: a processor coupled to a memory comprising instructions configured to: link a first set of acceleration components corresponding to a first set of the plurality of the servers into a first graph configured to accelerate a first service, wherein each of the first set of acceleration components is programmed to perform any of a first set of roles corresponding to the first service; link a second set of acceleration components corresponding to a second set of the plurality of the servers into a second graph configured to accelerate a second service, different from the first service, wherein each of the second set of acceleration components is programmed to perform any of a second set of roles corresponding to the second service; maintain in a storage a first address for the first graph such that the first service can request hardware acceleration from the first set of acceleration components; maintain in the storage a second address for the second graph such that the second service can request hardware acceleration form the second set of acceleration components; and in response to an increased demand for hardware acceleration from the second graph, based on an allocation policy: (1) switch, using configuration data and without loading a new image file, at least one of the first set of acceleration components from performing any of the first set of roles to performing any of the second set of roles, and (2) adjust at least one of the first address or the second address.
 9. The system of claim 8, wherein the first service is a service selected from among: document ranking, data encryption, data compression, speech translation, and computer vision.
 10. The system of claim 8, wherein the at least one acceleration component comprises at least one Field Programmable Gate Array (FPGA).
 11. The system of claim 8, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate balancing load across the hardware plane.
 12. The system of claim 8, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate minimizing switching of roles among acceleration components in the hardware plane.
 13. The system of claim 8, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate minimizing communication latency between acceleration components in the hardware plane.
 14. The system of claim 8, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the service manager is configured to monitor machine liveness of acceleration components in the hardware plane.
 15. A non-transitory computer storage medium comprising instructions corresponding to a method in a data center comprising a plurality of servers interconnected via a network, wherein each of the plurality of servers comprises at least one acceleration component, wherein the acceleration component comprises a plurality of hardware logic blocks interconnected using reconfigurable interconnects, the instructions configured to: link a first set of acceleration components corresponding to a first set of the plurality of the servers into a first graph configured to accelerate a first service, wherein each of the first set of acceleration components is programmed to perform any of a first set of roles corresponding to the first service; link a second set of acceleration components corresponding to a second set of the plurality of the servers into a second graph configured to accelerate a second service, different from the first service, wherein each of the second set of acceleration components is programmed to perform any of a second set of roles corresponding to the second service; maintain in a storage a first address for the first graph such that the first service can request hardware acceleration from the first set of acceleration components; maintain in the storage a second address for the second graph such that the second service can request hardware acceleration form the second set of acceleration components; and in response to an increased demand for hardware acceleration from the second graph, based on an allocation policy: (1) switch, using configuration data and without loading a new image file, at least one of the first set of acceleration components from performing any of the first set of roles to performing any of the second set of roles, and (2) adjust at least one of the first address or the second address.
 16. The non-transitory computer storage medium of claim 15, wherein the first service is a service selected from among: document ranking, data encryption, data compression, speech translation, and computer vision.
 17. The non-transitory computer storage medium of claim 15, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate balancing load across the hardware plane.
 18. The non-transitory computer storage medium of claim 15, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate minimizing switching of roles among acceleration components in the hardware plane.
 19. The non-transitory computer storage medium of claim 15, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the allocation policy is configured to facilitate minimizing communication latency between acceleration components in the hardware plane.
 20. The non-transitory computer storage medium of claim 15, wherein each of the first set of acceleration components and the second set of acceleration components is included in a hardware plane, and wherein the service manager is configured to monitor machine liveness of acceleration components in the hardware plane. 